Overview
CruiseControl.NET 0.7 is one of our largest single releases so far. If you are upgrading from 0.6.1 or earlier, there are some big changes. Some updates are:- Web Dashboard now has reporting options, allowing one web application instance to report multiple CruiseControl.NET projects across multiple servers. This feature is still in development, but see Web Dashboard Reporting Features for more details
- State Managers now automatically work for multi-project servers (so you should be able to take them out of your config file and forget about them!)
- The Xml log publisher now has default settings that work for multi-project servers (so you should just need an empty <xmllogger /> tag.) File merging has been removed from the Xml Logger, so you must use a File Merge Task for this behaviour.
- Some Source Control plugins can now automatically update your source tree for you (so no need for bootstrap builds). This feature is currently implemented by the CVS, Perforce and Visual Source Safe plugins.
- New <triggers> section replaces old <schedule> (See Trigger Blocks)
- Introduction of 'Working Directory' and 'Artifact' as Project-level concepts to make relative directories easier to use (see Project Configuration Block). More support for these concepts will be coming in later releases.
- Considerable documentation updates
We recommend that as part of upgrading that you backup your current CCNet directories, and then read the documentation thoroughly for the plugins you are using.
Some configuration options have changed since 0.6, so make sure you update your CCNet Config file before restarting.
Jira issues (0.7 RC-1 to 0.7)
Bug
CCNET-221 - Upgrading CCNet disables force build from cctray until one project is forced from dashboardCCNET-240 - images/check.jpg is missing
CCNET-242 - CCNet failing under .NET 1.0
Jira issues (0.6.1 to 0.7 RC-1)
This is a list of Jira issues that were marked resolved for CruiseControl.NET 0.7 RC-1. Note this list is not exhaustive of the work that went into 0.7 and it is recommended you follow the instructions above if upgrading. This list can be read online at http://jira.public.thoughtworks.org/secure/ReleaseNote.jspa?projectId=10000&styleName=Html&version=10050Bug
CCNET-21 - Modifications generated by FileSystem SC break EmailPublisher (Wilka Hudson)</li>
CCNET-25 - pvcstemp.txt file is not correct for some versions of PVCS</li>
CCNET-45 - CCNet console throws an exception when using -help flag</li>
CCNET-61 - Force build on initial start up instead of detecting all mods between now and Jan 1, 1980</li>
CCNET-79 - Daily schedule doesn't work right</li>
CCNET-94 - CCNet server does not work with HttpChannel</li>
CCNET-99 - Collapse/Expand javascript doesn't work with Mozilla</li>
CCNET-102 - Path variable Null Exception for VSS</li>
CCNET-104 - compile.xsl does not find warnings and errors correctly</li>
CCNET-116 - IntegrationStateManager saves files with the incorrect encoding.</li>
CCNET-118 - Pb with VSS history parsing when a project contains a folder named "added"</li>
CCNET-120 - "port in use" remoting exception</li>
CCNET-135 - EMailPublisher not handling null Modification user</li>
CCNET-157 - Service not auto-flushing its log</li>
CCNET-168 - Default.aspx throws "Expression must evaluate to a node-set." Exception</li>
CCNET-174 - Perforce View Validation breaks on paths withs spaces</li>
CCNET-175 - '-' is not handled in filenames</li>
CCNET-176 - NAnt Build Is Failing</li>
CCNET-182 - Vault output is not necessarily valid xml</li>
CCNET-184 - NAnt <builderror> elements were not getting correctly included in the web page</li>
CCNET-190 - Fixing dashboard URL Mapper to handle server ports</li>
CCNET-209 - WebApp Web.config must start by configSections tag instead of appSetting tag</li>
CCNET-210 - Trim CCTray URL</li>
CCNET-214 - NAnt output being put in CData section in Xml Log</li>
New Feature
CCNET-16 - Implement ModificationFilter SourceControl</li>CCNET-24 - French language support for Vss</li>
CCNET-43 - Create a non-polling Schedule</li>
CCNET-100 - Cvs needs to get source</li>
CCNET-101 - Ignore fields</li>
CCNET-143 - Deleting a project from the webapp should delete the working directory</li>
CCNET-145 - Perforce plugin should delete working directory and client spec on Project Delete</li>
CCNET-146 - XmlLogPublisher should use sensible default directory</li>
CCNET-147 - WebApp should generate default 'Project URL'</li>
CCNET-152 - Merge Files Task should use project working directory</li>
CCNET-171 - Support Multiple Schedules</li>
CCNET-201 - Relative log directories in XmlLogger should be relative to Project Artifact Directory</li>
CCNET-202 - Remove merge files code from XmlLogPublisher</li>
CCNET-215 - DevEnv Builder should support relative location for solution file</li>
CCNET-216 - FileSourceControl should implement GetSource()</li>
Task
CCNET-139 - Log VSS date parsing errors</li>
CCNET-183 - Apply ASP.NET Security Fix</li>
CCNET-195 - Bring Documentation up to date for 0.7 release</li>
Improvement
CCNET-37 - Eliminate duplicated stylesheets</li>CCNET-56 - Assemblies to be versioned correctly</li>
CCNET-89 - Perforce Plugin should support 'GetSource'</li>
CCNET-103 - Use XPathDocument instead of XMLDocument when doing XSLT to significantly boost peformance.</li>
CCNET-106 - Show CCTray connection error dialog as a balloon (Bruce Hearn)</li>
CCNET-107 - Project name should be included in the state file name</li>
CCNET-114 - Allow Tray Icon configuration in CCTray</li>
CCNET-115 - Reformat Test Details page and show it collapsed on front page</li>
CCNET-138 - auto-replace in vss source control</li>
CCNET-166 - Patch to Add UserName and Password to SVN Task</li>
CCNET-177 - Checkin time included in reports</li>
CCNET-185 - Encapsulate Vault cmd line parameters in quotes</li>
CCNET-191 - AutoGetSource For Starteam</li>
CCNET-197 - Rename 'schedule'</li>
CCNET-198 - Separate 'Integration Triggering' from 'Project Stopping'</li>
